WEBVTT Kind: captions 00:00:20.119 --> 00:00:26.869 position:63% line:0% Hello everybody! Dualbooting is a great way to try other setups without losing any data 00:00:26.869 --> 00:00:29.789 position:63% line:0% as well as retaining full compatibility with otherwise 00:00:29.789 --> 00:00:35.500 position:63% line:0% out of reach software. A prime example of dualbooting should be Windows 10 and 00:00:35.500 --> 00:00:41.890 position:63% line:0% a linux distro sharing the same machine. Here on my channel though I like to take ju-ust 00:00:41.890 --> 00:00:43.380 position:63% line:0% a bit too far. 00:00:43.380 --> 00:00:48.309 position:63% line:0% Today I will attempt to dualboot Windows 98 and Windows 11. 00:00:48.309 --> 00:00:53.989 position:63% line:0% Now you might be thinking - that's impossible! These operating systems are way too far apart 00:00:53.989 --> 00:00:57.780 position:63% line:0% to be installed on the same machine! Well, you are partially 00:00:57.780 --> 00:01:03.129 position:63% line:0% correct - it is indeed impossible to get it working on 99% of the hardware, 00:01:03.129 --> 00:01:08.640 position:63% line:0% especially with Windows 11 enforcing more new imaginary hardware limitations and Windows 00:01:08.640 --> 00:01:13.670 position:63% line:0% 98 slowly disappearing in the abyss of past. Despite such an age gap, 00:01:13.670 --> 00:01:17.399 position:63% line:0% there's some hardware in the middle that still can boot both Windows 98 00:01:17.399 --> 00:01:24.899 position:63% line:0% and Windows 11. I happen to own a laptop that *apparently does* boot them. It's the newer 00:01:24.899 --> 00:01:28.149 position:63% line:0% Sandy Bridge Lenovo G570. 00:01:28.149 --> 00:01:33.929 position:63% line:0% The older one did not boot Windows 98 for some reason. More on that later, meanwhile 00:01:33.929 --> 00:02:05.149 position:63% line:0% take a look at the specs of this rocker. 00:02:05.149 --> 00:02:10.379 position:63% line:0% And with that, let's begin the install! I will get Windows 98 going first, because it 00:02:10.379 --> 00:02:15.240 position:63% line:0% might scream about an existing NTFS partition or literally everything else, 00:02:15.240 --> 00:02:18.010 position:63% line:0% I don't even want to imagine what would happen if Windows 11 was present 00:02:18.010 --> 00:02:23.800 position:63% line:0% during the 98 setup process. Anyway, here's the CD of it. 00:02:23.800 --> 00:02:32.680 position:63% line:0% First of all, SATA controller mode must be set to compatible, because Windows 98 does 00:02:32.680 --> 00:02:47.769 position:63% line:0% not support AHCI, what did you expect? Obviously, you can't just outright install 00:02:47.769 --> 00:02:53.080 position:63% line:0% it after tweaking the controller mode either. The DVD-rom won't work at all. 00:02:53.080 --> 00:03:01.670 position:63% line:0% Don't worry, though, it's not necessary to set up Windows 98. Sounds pretty dumb, but 00:03:01.670 --> 00:03:06.769 position:63% line:0% it's just a nasty workaround. What I will do is I'll boot to Windows 11 00:03:06.769 --> 00:03:10.080 position:63% line:0% installer, partition the disk for Windows 98, copy the installation files 00:03:10.080 --> 00:03:34.290 position:63% line:0% in a separate directory and start the installation from a hard drive. 00:03:34.290 --> 00:04:26.520 position:63% line:0% All right, there's the partition I've made and the win98 folder 00:04:26.520 --> 00:04:32.370 position:63% line:0% containing all necessary installation files. I'll just run 00:04:32.370 --> 00:04:38.030 position:63% line:0% setup.exe from there, and we'll be good to go. 00:04:38.030 --> 00:04:49.310 position:63% line:0% And we are in! 00:04:49.310 --> 00:05:44.000 position:63% line:0% Obviously, there's an NTFS caution, but it's just a caution, so we can skip it. The copying 00:05:44.000 --> 00:05:49.970 position:63% line:0% process flows without any errors. But here we run into a big issue. 00:05:49.970 --> 00:05:55.389 position:63% line:0% Remember, this machine has 4 gigabytes of RAM, which is a theoretical limit of 00:05:55.389 --> 00:06:02.940 position:63% line:0% a 32-bit system, and it is running. a. system. from. 1998. *giggle* Back then even a single 00:06:02.940 --> 00:06:08.190 position:63% line:0% gigabyte of RAM was considered absolutely gigantic and massive. Think about 00:06:08.190 --> 00:06:13.710 position:63% line:0% Linus' 1 terabyte of RAM setup. Yes, that's exactly what was thought of a 00:06:13.710 --> 00:06:16.150 position:63% line:0% gigabyte back then. 00:06:16.150 --> 00:06:22.350 position:63% line:0% This is a huge issue. Let alone theoretical 4, Windows 98 was limited just to a gigabyte 00:06:22.350 --> 00:06:28.470 position:63% line:0% of RAM. Want to know why? There was a certain OEM that decided to create 00:06:28.470 --> 00:06:33.540 position:63% line:0% a beastly machine with Windows 98 onboard. Not like they could have 00:06:33.540 --> 00:06:38.140 position:63% line:0% used Windows NT, but Microsoft surprisingly accepted that offer and amped up the memory 00:06:38.140 --> 00:06:42.650 position:63% line:0% limit to 1 gigabyte. They did sacrifice the minimum memory requirement 00:06:42.650 --> 00:06:56.379 position:63% line:0% for that stunt, though. All due to the nature of memory manager Windows has. 00:06:56.379 --> 00:07:02.230 position:63% line:0% Either way, that's not the point. What can we do with that thing? Lucky for us, there 00:07:02.230 --> 00:07:07.460 position:63% line:0% was a fantastic programmer Rudolph Loew, which was primarily writing 9x patches and 00:07:07.460 --> 00:07:12.789 position:63% line:0% compatibility fixes to help these versions run on newer hardware. One of them 00:07:12.789 --> 00:07:17.349 position:63% line:0% exactly patches the virtual memory manager to accept those theoretical 4 gigabytes of 00:07:17.349 --> 00:07:22.750 position:63% line:0% RAM. Just so you know, Windows 11 minimum memory requirement is exactly 4 gigabytes. 00:07:22.750 --> 00:07:26.189 position:63% line:0% This dualboot is on a real thin ice there! 00:07:26.189 --> 00:07:29.720 position:63% line:0% *q* Just kidding, Windows 11 requirements are a meme 00:07:29.720 --> 00:07:34.039 position:63% line:0% Anyway, to install that patch I will just copy it over using a Windows 11 installer 00:07:34.039 --> 00:08:09.259 position:63% line:0% and run it inside a command prompt mode. Now Windows 98 boots with a full RAM set. 00:08:09.259 --> 00:08:20.180 position:63% line:0% The 00:08:20.180 --> 00:08:23.960 position:63% line:0% driver setup begins, that's the most unnerving part of installing Windows 98 00:08:23.960 --> 00:08:26.909 position:63% line:0% on seemingly unsupported hardware. 00:08:26.909 --> 00:08:35.600 position:63% line:0% Aaaand, we get a blue screen. This is exactly the part where my old G570 got completely 00:08:35.600 --> 00:08:43.789 position:63% line:0% denied. It would just get to that part and always throw a blue screen. (Hey, 00:08:43.789 --> 00:08:50.370 position:63% line:0% that's a cool effect, actually.) 00:08:50.370 --> 00:09:08.970 position:63% line:0% Let's restart... and, just as if nothing happened, it continues the setup. 00:09:08.970 --> 00:09:16.410 position:63% line:0% We take what we can get, I got no issue with that. 00:09:16.410 --> 00:09:47.620 position:63% line:0% The rest of the setup goes well. So, with that, Windows 98 was installed. and... that's 00:09:47.620 --> 00:09:49.490 position:63% line:0% it? 00:09:49.490 --> 00:09:52.670 position:63% line:0% You thought that was it, right? Well, you're WRONG! We've got unfinished business here! 00:09:52.670 --> 00:09:57.420 position:63% line:0% (gotta set the cloud wallpaper first) Let's deploy a bunch of drivers on it! Or, 00:09:57.420 --> 00:10:01.120 position:63% line:0% at least, attempt to. 00:10:01.120 --> 00:10:26.360 position:63% line:0% First I installed the USB patch, then the 9x unicode layer, then the sound blaster driver 00:10:26.360 --> 00:10:35.170 position:63% line:0% for kicks and giggles (it didnt install) and finally, the VBEMP 00:10:35.170 --> 00:10:47.980 position:63% line:0% display driver, which worked. 16:9 display patches don't work in conjunction 00:10:47.980 --> 00:10:58.699 position:63% line:0% with that driver, so I didn't even bother to try them. 00:10:58.699 --> 00:11:02.870 position:63% line:0% And with that, Windows 98 was pretty much finished. That's probably the best you can 00:11:02.870 --> 00:11:53.880 position:63% line:0% set it up on new hardware. Let's move onto the Windows 11 meme. Oh, sorry, 00:11:53.880 --> 00:11:56.090 position:63% line:0% didn't mean to say the last word, my bad... 00:11:56.090 --> 00:12:02.290 position:63% line:0% This laptop doesn't support Windows 11. That means we can freely install it on this bad 00:12:02.290 --> 00:12:11.550 position:63% line:0% boy with almost no effort. With a few magic registry keys we can bypass 00:12:11.550 --> 00:12:45.509 position:63% line:0% all the Windows 11 requirements and continue with the installation. 00:12:45.509 --> 00:12:51.690 position:63% line:0% I'll skip the first time setup, by this point it's already stale and generic to show. Gotta 00:12:51.690 --> 00:13:21.690 position:63% line:0% appreciate that screen though, it's looking damn good. 00:13:21.690 --> 00:13:29.899 position:63% line:0% I'll set the dark theme and a wallpaper, of course put the taskbar to the left, since 00:13:29.899 --> 00:13:41.120 position:63% line:0% it being centered is just an insult to Windows. family of products. Finally, I just have to 00:13:41.120 --> 00:13:46.089 position:63% line:0% set up the dualboot. People actually suggest to install newer versions first to 00:13:46.089 --> 00:13:51.839 position:63% line:0% enjoy the perks of automatic bootloader setup, but let's be real, we have hands and knowledge 00:13:51.839 --> 00:13:54.279 position:63% line:0% and we can set up a bootloader ourselves. 00:13:54.279 --> 00:14:00.209 position:63% line:0% First, we create the Windows 98 bootloader entry and specify that it uses a boot sector 00:14:00.209 --> 00:14:06.980 position:63% line:0% instead of a Windows loader. Next, we set the first volume as a boot source 00:14:06.980 --> 00:14:11.750 position:63% line:0% (remember that partition and volume symlink indexes begin with 1) 00:14:11.750 --> 00:14:16.970 position:63% line:0% Now we need to set the 98 bootloader path, which is in fact a copy of the boot sector, 00:14:16.970 --> 00:14:20.089 position:63% line:0% the first sector on our logical drive. 00:14:20.089 --> 00:14:37.560 position:63% line:0% Finally, I'll put that boot entry to the bottom, so the WINDOWS 10 is on the top. And that's 00:14:37.560 --> 00:14:44.190 position:63% line:0% pretty much it for the dualboot part. So, just to clarify, both Windows 00:14:44.190 --> 00:15:35.050 position:63% line:0% versions boot and function correctly. Here's 98 and here's 11 (or 10) 00:15:35.050 --> 00:15:48.249 position:63% line:0% I hope you enjoyed the video. Thanks you all so much for watching. Take care.